Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added the doc so I had something to push, and we could have a discussion here on exactly what should go where.
I think we should have 3 queues:
Where
critical
means 'a user will need this',dhis2-safe
means 'we won't hurt the dhis much'?, and 'default' means 'run this when the other two are done'.If someone or something now enqueues 300 large invoices, we will still have delays, because the workers will pick 16 items of the default queue and we will only process the
critical
queue once a worker becomes free again.If we really, really wanted to have critical always working, we would need to start two sidekiq process, I think.
So below, our workers and how I would divide them: